server/utils/docs/text.ts (1)

138-141: Consider using forEach for type-safe iteration.

The non-null assertion highlightedCodeBlocks[i]! bypasses TypeScript's type checking. While the loop bounds guarantee valid indices, a forEach callback would be strictly type-safe without the assertion.

♻️ Suggested refactor

-  for (let i = 0; i < highlightedCodeBlocks.length; i++) {
-    const highlighted = highlightedCodeBlocks[i]!
-    result = result.replace(`__CODE_BLOCK_${i}__`, highlighted)
-  }
+  highlightedCodeBlocks.forEach((highlighted, i) => {
+    result = result.replace(`__CODE_BLOCK_${i}__`, highlighted)
+  })

As per coding guidelines: "Ensure you write strictly type-safe code, for example by ensuring you always check when accessing an array value by index".

server/utils/docs/render.ts (1)

138-161: Destructured array elements may be null despite conditional guards.

The variables highlightedSignature, renderedDescription, and renderedJsDocTags are typed as string | null. The conditionals at lines 144, 154, and 159 mirror the conditions used to create the promises, but TypeScript cannot correlate these checks.

The runtime behaviour is correct, but for stricter type safety, consider using truthiness checks directly on the resolved values (which you already do at lines 154 and 159) or adding explicit null checks.

♻️ Minor type-safe adjustment for line 145

   if (signatures.length > 0) {
-    lines.push(`<div class="docs-signature">${highlightedSignature}</div>`)
+    lines.push(`<div class="docs-signature">${highlightedSignature ?? ''}</div>`)